You are here: Building the Model: General Elements > Processing > Routing Edit Table > Routing Rule Dialog Box
The Routing Rule dialog box provides methods for selecting an entity's destination after finishing a process. The Rule heading button in the Routing edit table, brings up the Routing Rule dialog box. The fields of this dialog box are defined in the following example.
Start new block Check this box to signal the beginning of a new routing block. Checking this box will place a number in the Blk field for that record.
New Entity Check Box In order to let you designate whether a routing block applies to the main entity or if you wish to create a new entity, ProModel includes a New Entity check box in the routing rule dialog. By default, ProModel does not check the first routing block for a process record but does check subsequent blocks unless they share the same input and output name. If you check the New Entity box, an asterisk (*) appears after the block number in the block column of the routing table.
If you check the new entity box, the entity using the routing block will begin routing with new cost and time statistics. If the new entity box remains unchecked, ProModel assumes the entity routing from this block is a main entity (the parent entity), carrying with it all cost and time statistics.
If the new entity field remains unchecked and you enter a quantity field value greater than 1, ProModel behaves just as it does with a SPLIT AS statement, dividing the cost statistics between the split members and resetting all time statistics to zero.
Please note
A run-time error occurs if you fail to route one (and only one) main entity for a process. If no routing block executes for the main entity, a "No routing defined for main entity" error occurs. If more than one route block executes for the main entity, a "Main entity already routed" error occurs.
Quantity The number of entities resulting from this routing block. The default is one. Several entities of the same name can be created from a single entity, much like a split AS statement, by entering a number greater than one. Each of the new entities then processes the routing block one entity at a time. For example, suppose an entity called mail_bag enters a location and is separated into 30 individual pieces of mail, called Letters. Enter 30 as the quantity and Letter as the output entity, as in the example below. Only the first line in a routing block can specify a quantity.
Process Table
|
Entity |
Location |
Operation (min) |
|---|---|---|
|
mail_bag |
Loc1 |
WAIT T(2,5,8) |
Routing Table
|
Blk |
Output |
Destination |
Rule |
Move Logic |
|---|---|---|---|---|
|
1 |
Letter |
Loc2 |
FIRST 10 |
MOVE FOR 1 |
Routing Rules Choose the rule for selecting the next location. Only one rule may be chosen for each routing line. Note that the last three routing rules, alternate, backup and dependent, may not be chosen as the start of a new routing block. Note also that no more than one of the other rules can appear in a single block (e.g., you cannot mix a First Available rule and a Most Available rule in the same block).
For exact syntax and examples of each routing rule, see Routing Rules.